Skip to content

docs(CSM-341): explain Android double package cause in Testing Distribution FAQ#3

Open
arcappcircle wants to merge 1 commit into
developfrom
feature/CSM-341
Open

docs(CSM-341): explain Android double package cause in Testing Distribution FAQ#3
arcappcircle wants to merge 1 commit into
developfrom
feature/CSM-341

Conversation

@arcappcircle

@arcappcircle arcappcircle commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Expands the Testing Distribution FAQ entry "No files or multiple files were received from autodistribute" to explain why two Android packages are distributed and how to avoid it.

When an Android project defines its own gradle sign config and the Appcircle Android Sign step is enabled, the build produces two signed APK artifacts and AutoDistribute sends both to the distribution profile (this happens even with auto-send). The doc now documents the two-binary origin, the single-signing-path resolution, and the AAB convert option via Auto Re-sign.

Context

  • Zendesk ticket #1169
  • Linear: CSM-341 (sub-issue of CSM-332)

Changes

  • docs/testing-distribution/create-or-select-a-distribution-profile.md - new "Why two Android packages are distributed" subsection + AAB convert note under the FAQ.
  • docs/workflows/android-specific-workflow-steps/android-build.md - caution note cross-linking the FAQ section.
  • docs/workflows/android-specific-workflow-steps/android-sign.md - caution note cross-linking the FAQ section.

Migrated from appcircle-docusaurus#1249.


Created on behalf of ozcan@appcircle.io via Arc.

Summary by CodeRabbit

  • Documentation
    • Added guidance explaining why some Android builds may appear as two packages in Testing Distribution.
    • Clarified that using both project signing and the Android signing step can create duplicate APK artifacts.
    • Added recommendations to use only one signing method to avoid distributing multiple packages.
    • Included a note that AAB files must be converted to APK before sending to test devices.

@arcappcircle arcappcircle requested a review from SarpBakis23 as a code owner July 7, 2026 11:58
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6d3d99c8-f7d2-408f-b25a-57ce8f1f92e0

📥 Commits

Reviewing files that changed from the base of the PR and between 9d9a9eb and 650cbb5.

📒 Files selected for processing (3)
  • docs/testing-distribution/create-or-select-a-distribution-profile.md
  • docs/workflows/android-specific-workflow-steps/android-build.md
  • docs/workflows/android-specific-workflow-steps/android-sign.md

📝 Walkthrough

Walkthrough

This PR adds documentation explaining that enabling both Gradle signing and Appcircle's Android Sign build step produces two separately signed APK artifacts. Caution notes were added to the Android Sign and Android Build docs, plus a new FAQ entry in the Testing Distribution profile doc.

Changes

Android dual-signing documentation

Layer / File(s) Summary
Signing caution notes
docs/workflows/android-specific-workflow-steps/android-sign.md, docs/workflows/android-specific-workflow-steps/android-build.md
Adds "Two signed packages" caution blocks explaining that enabling both Gradle signing and Android Sign produces duplicate APK artifacts, with guidance to disable one signing path.
FAQ entry
docs/testing-distribution/create-or-select-a-distribution-profile.md
Adds a new FAQ item "Why two Android packages are distributed," detailing the dual-artifact behavior, auto-distribution impact, remediation, and an AAB-to-APK conversion note.

Sequence Diagram(s)

No sequence diagram generated as these are documentation-only text additions.

Poem

Two APKs hop out the door,
Signed twice—now who needs more?
This bunny writes the docs with care,
One signing path, a cleaner pair. 🐰
Hop along, read on, beware!

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main documentation update about why Android builds can produce two distributed packages.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/CSM-341
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch feature/CSM-341

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)


Comment @coderabbitai help to get the list of available commands.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
appcircle-docs 650cbb5 Commit Preview URL

Branch Preview URL
Jul 07 2026, 12:00 PM

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
appcircle-docs 650cbb5 Commit Preview URL

Branch Preview URL
Jul 07 2026, 12:00 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants